Taking into account new TLS 1.3 field from domain-scan #17
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
As of 4/4/2018, domain-scan is checking for TLS 1.3 support when scanning with sslyze. This injects a field into the CSV output of sslyze, and this commit makes the necessary adjustments for that.
jsf9k
added a commit
that referenced
this pull request
Nov 4, 2022
…t_autoupdate Add updates from running pre-commit autoupdate
jsf9k
pushed a commit
that referenced
this pull request
Nov 4, 2022
…ates Pull in updates from skeleton-generic
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since 18F/domain-scan#221 was merged,
domain-scanis checking for TLS 1.3 support when scanning withsslyze. This injects an additional field into the CSV output ofdomain-scan, and this commit makes the necessary adjustments for that.